bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Tue, 24 Sep 2019 19:09:57 +0000 (20:09 +0100)
committerSylvestre Ledru <sylvestre@debian.org>
Tue, 24 Sep 2019 19:09:57 +0000 (20:09 +0100)
commit22fb0e82df217f64fb52b2839dd50a4eae18cda3
treebe158754e89174bdc29fe9a0928da651146aa4a8
parent0d680f3ee89a9fc2482d814051765a3ae32ea903
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h